Atlassian Data Center End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Atlassian Data Center versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| End of Sale — New Customers | Data Center | Jan 1, 2016 | Mar 30, 2026 | 152 days past EOL | EOL |
| End of Sale — Existing Customers | Data Center | Jan 1, 2016 | Mar 30, 2028 | 579 days remaining | Active |
| Data Center Support (Jira, Confluence) LTS | Data Center | Jan 1, 2016 | Mar 28, 2029 | 942 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/atlassian-data-center)
Atlassian Data Center lifecycle status — the real story
Atlassian has now retired all three of its self-managed licensing tiers in sequence. Server reached end of life February 15, 2024 — no further security patches for any Server product. Data Center is now on the same clock: new-customer sales ended March 30, 2026; existing customers can still renew or expand Data Center and Marketplace app licenses through March 30, 2028; and on March 28, 2029, all Data Center licenses expire and the software switches to read-only — installations keep running but stop receiving updates, and stop functioning as licensed software once the license check fails.
The three licensing models are easy to conflate but behave very differently at end of life: Server is already fully unsupported; Data Center is self-hosted but time-boxed to the 2029 date above, with Atlassian committing to technical support and critical-severity security fixes only through that date; Cloud is Atlassian's actively developed, indefinitely supported product and the only tier with no published end date. Atlassian's own guidance is unambiguous: migrate to Cloud, and Data Center exists mainly as a bridge for organizations with hosting, compliance, or data-residency requirements Cloud can't yet meet.
One notable exception: Bitbucket Data Center will not reach end of life on the 2029 date — Atlassian is instead offering existing Bitbucket Data Center customers a hybrid license covering both Data Center and Cloud, so treat Bitbucket separately from Jira and Confluence Data Center when assessing exposure. As with any vendor's published EOL policy, dates and program details (the hybrid-license terms in particular) can be refined before they take effect — the practical takeaway for any organization still on Data Center is that the runway is now fixed in years, not indefinite, and migration planning should start well before the 2028 renewal cutoff, not the 2029 expiry.
Atlassian Data Center release and support pattern
Across the 3 release lines with a published release date, Atlassian Data Center has shipped a new line roughly every 1 weeks (median interval). A line typically stays supported for about 12.2 years from its release to its end-of-life date. 1 of the 3 tracked lines is designated long-term support, which is where the longer windows sit.
Of the 3 release lines tracked, 1 is past end of life and 2 are still within support. The newest line, Data Center Support (Jira, Confluence), was released January 1, 2016. The next scheduled end of life is End of Sale — Existing Customers on March 30, 2028 — 578 days from this build. The longest-supported line currently published is Data Center Support (Jira, Confluence), to March 28, 2029.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Atlassian Data Center security intelligence
CISA KEV history: Atlassian Data Center is named in CISA's Known Exploited Vulnerabilities catalog 10 times, most recently on 2024-11-12, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does Atlassian Data Center end of life mean for your organization?
When a version of Atlassian Data Center reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Atlassian Data Center should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Atlassian Data Center reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Atlassian Data Center versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Atlassian Data Center has 1 version past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Atlassian Data Center is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."